-
Notifications
You must be signed in to change notification settings - Fork 1.8k
CNV-68980: Must gather image #102013
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
CNV-68980: Must gather image #102013
Conversation
|
@erpeters157: This pull request references CNV-68980 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.21.0" version, but no target version was set. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
🤖 Mon Nov 10 20:09:59 - Prow CI generated the docs preview: |
| If you encounter issues with {IBMFusionFirst}, provide the must-gather image with the other information provided to Red Hat support. This image contains critical data about your cluster and project resources, logs, and events from your deployment. The following command is used to create the image: | ||
|
|
||
| ---- | ||
| $ oc adm must-gather --image=icr.io/cpopen/ibm-spectrum-scale-must-gather:v5.2.3.1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
v5.2.3.1 is a specific version
Do we want to replace it with something like:
oc adm must-gather --image=icr.io/cpopen/ibm-spectrum-scale-must-gather:v<CNSA version> ?
The CNSA version can be retrieved with:
oc get fusionaccesses.fusion.storage.openshift.io -n ibm-fusion-access fusionaccess-sample -o jsonpath='{.spec.storageScaleVersion}'
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@achuzhoy Thank you for the clarification. That is a great suggestion. I will implement the update.
|
/lgtm |
|
@erpeters157: This pull request references CNV-68980 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.21.0" version, but no target version was set. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
/lgtm |
|
@erpeters157: This pull request references CNV-68980 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.21.0" version, but no target version was set. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
ousleyp
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a few comments and suggestions. Please feel free to ping me if you have any questions. Thanks, Erin!
|
New changes are detected. LGTM label has been removed. |
42574ce to
b1139c6
Compare
|
@erpeters157: all tests passed! Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
abrennan89
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a few minor changes. Good work! 🙂
| [id="troubleshoot-fusion-access-san_{context}"] | ||
| = Troubleshooting {IBMFusionFirst} | ||
|
|
||
| If you encounter issues with {IBMFusionFirst}, provide the must-gather image to Red{nbsp}Hat support. This image contains critical data about your cluster and project resources, logs, and events from your deployment. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| If you encounter issues with {IBMFusionFirst}, provide the must-gather image to Red{nbsp}Hat support. This image contains critical data about your cluster and project resources, logs, and events from your deployment. | |
| [role="_abstract"] | |
| If you encounter issues with {IBMFusionFirst}, provide the `must-gather` image to Red{nbsp}Hat support. This image contains critical data about your cluster and project resources, logs, and events from your deployment. |
Per the CQA 2.0 guidelines, alll abstracts need this little tag :) ref: https://docs.google.com/spreadsheets/d/1wF_NUWXBJaYsaXp8Dn6TQOx9gD45NCqNxaPkXhYN-zI/edit?gid=503904153#gid=503904153
|
|
||
| .Procedure | ||
|
|
||
| . To obtain the deployed version of {IBMFusionFirst}, use the following command: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| . To obtain the deployed version of {IBMFusionFirst}, use the following command: | |
| . To obtain the deployed version of {IBMFusionFirst}, run the following command: |
Use "enter" or "run" per the OCP doc guidelines: https://github.com/openshift/openshift-docs/blob/main/contributing_to_docs/doc_guidelines.adoc#procedure-step-that-introduces-a-command
| This command returns the numeric value of the deployed version of {IBMFusionFirst} such as `2.11.0`. | ||
| ==== | ||
|
|
||
| . To create the must-gather image, use the following command: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| . To create the must-gather image, use the following command: | |
| . To create the `must-gather` image, use the following command: |
Funny enough, I went to check on this, and you can see in https://docs.redhat.com/en/documentation/openshift_container_platform/4.20/html/support/gathering-cluster-data#gathering-data-specific-features_gathering-cluster-data where it's formatted differently for Virtualization versus regular OCP 🤭
I think it should be formatted as "must-gather image" but we probably need a follow up Jira to fix it in other places in the docs too.
Add information about producing the must-gather image for IBM Fusion SAN troubleshooting.
Version(s):
4.20+
Issue:
CNV-68980
Link to docs preview:
Troubleshooting IBM Fusion Access for SAN
QE review:
Additional information: